File Check ESE Utility

The File Check ESE utility (FileChkESE.exe) is a command-line utility that performs internal logical consistency checks for the ESE-based datastore file (.dat.edb). It primarily checks for several different types of errors including, record length inconsistencies, two types of orphaned records, and database record count mismatches.

For example, File Check ESE could be used in the following situation: If the hard disk fails and backups are disabled (or if backups are also corrupted due to the disk failure) and ESENTUTL’s Repair option is used, and since some records may be lost, the recovered databases may not be in a "CygNet DBS consistent" state. That is, record counts may not match, the internal indexes in the .dat.edb file may point to newly missing records, and records may exist without their parent (for example, a UIS command is defined for a device that was unable to be recovered). Run FileChkESE to perform a consistency check against the recovered database to identify these types of errors. You would also run ReIndexESE in this case to rebuild the ESE Index file.

This utility requires that the DBS-based service be stopped.

Syntax

FileChkESE ConfigFileName [A or H or L] /fix_errors /allow_destructive

Parameters

If no parameters are specified, the utility uses the configuration file in the startup directory, and performs all checks.

Parameter Definition

ConfigFileName

The name of the service configuration file. If no ConfigFileName is specified, the utility will use the configuration file in the startup directory.

[A | H | L]

Required switch to indicate which check(s) to perform.

A Performs both H and L checks
H Checks to see if the header status reports a clean shutdown
L Performs the internal logical consistency checks

If a switch is not specified all checks will be performed. The switch is case sensitive. Use UPPERCASE.

/fix_errors

Repairs most "simple" errors.

/allow_destructive

This parameter will enable further fixes that may be more destructive in nature.

Note: It may be a better option to restore from backup using the DBSRESTOREBACKUP utility. Not all errors can be reliably be fixed with /allow_destructive. See DBS Restore Backup Utility for more information.

Example

FileChkESE C:\CygNet\Services\GNS\Gns.cfg A /fix_errors /allow_destructive